Updated Raspberry install docs. #1243
Conversation
There was a problem hiding this comment.
Thank you very much! The docs are very much in need of such contributions and I think, this can be very valuable to first time users as you say.
I added many small comments. You don't need to tackle them all at once. If you prefer, we can also fix the basic formatting things, merge and improve gradually from there.
Co-authored-by: eladyn <[email protected]>
Co-authored-by: eladyn <[email protected]>
Co-authored-by: eladyn <[email protected]>
Co-authored-by: eladyn <[email protected]>
Co-authored-by: eladyn <[email protected]>
I am glad you say this, I wasn't sure if this kind of detailed documentation was really wanted. :) I would merge now, maybe you can do before what I proposed in the comments and then the work can continue from the merge. I was also thinking of adding instrcutions how to build from the latest release source and not from the latest commit, but I would do that afterwords. Thank you for your frinedly response! |
Co-authored-by: eladyn <[email protected]>
| ## Known issues / Logging | ||
| Logging in files is currently not possible for the daemon setup, the daemon crashes without the --no-daemon argument (redirects the output to stdout). | ||
| Without the parameter it tries to output at syslog, but even with syslog installed it crashed. | ||
| To get at least the latest output run | ||
|
|
||
| ```bash | ||
| sudo systemctl status spotifyd.service | ||
| ``` |
There was a problem hiding this comment.
Maybe we could remove this part before we merge, since this is probably not accurate.
There was a problem hiding this comment.
Ok I took this and the whole discussion as an opportunity to overwork the docs again. Most of the topics were general Linux topics, so I separated the system/sistribution specific topics and the general Linux topics. General topics are now in 'Build-on-Linux.md' and 'Run-on-Linux.md', the specific files like Raspberry files are now just a small entry point with few specific topics and links to the general files. At least the run file can also be linked in the Fedora file and maybe also in the FreeBSD file I think.
From the known issues I removed the logging issue, but added the DnsSdError and new issue: I switch to the PulseAudio backend because I have short overlaps of Spotify and radio playback on my app, which caused it to crash, because my HifiBerry amp isn't capable of mixing 2 audio streams in hardware. But as a system wide service, I get a connection refused error when accessing the PulseAudio backend, first I thought I cannot access a service run as user (which PulseAudio is) from a process run as root, but I configured the system service to run with my normal user and the problem persists. I found here: #685 that it may be an issue with RuntimeDirectory of system services, but I didn't had the time yet to investigate it further. If you know this and have a solution, you can remove the issue and maybe tell me the solution. ;) Otherwise I try to find a solution next year.
And I also tried to unified some wordings like the use of compile/build and daemon/service.
So far, have a nice christmas and holiday season!
There was a problem hiding this comment.
If I can also help updating instructions on the homepage, just let me know how.
Or if I shall build ARM64 binaries for the download page I can also do it.
|
Hello, I just saw that this is still open, do you need any action or information from me? Or was it just not on your schedule yet? |
|
I'm sorry for not following up with anything. Initially I planned to have another look at your PR and then merge it, but as time passed I got more and more convinced that something had to be done to the entire docs. As this is a larger project, I only started working on it and never finished it since then. The biggest thing that I noticed that should be done before we can merge is to change |
|
I see what you mean, also some conent seems a little bit redundant in the readme and other files... |
|
I cleand up my repositories and also deleted the spotifyd fork, I wasn't aware that I still had an open pull request. :D |
|
Oh thank you! I was already wondering what happened. I hope to finally get around to doing documentation things in a few weeks, but maybe I can just see if merging this is possible since it would have been helpful in multiple occasions already. |
Hello,
I really appreciate the work you put is in this project. I am currently building an Internetradio on Raspberry basis, for which I also wanted spotify integration. Therefore I need a little control over the Spotify service on the Raspberry itself, e.g. stopping the Spotify playback when I chose a radio station and the radio starts playing. I found spotifyd as a possible solution for this use case, but I had a hard time setting it up for my needs.
I want to share my experience and enriched the documentation with topics, where I had trouble. As I am not so deep in the techincal topics like Rust and Linux, I try at leas to contribute at the docs...
I still see 2 problems which I couldn't solve, but for which I have workarounds, but I will open issues for these.
Best regards
Matthias